-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Cleanup meta field docs #10912
Conversation
} | ||
} | ||
-------------------------------------------------- | ||
Note, even though the `_type` is not indexed, all the APIs still work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, but it IS indexed, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! This was a mistake, I reworded the _type
docs.
As a side note, shouldn't we remove the ability to configure store/index on timestamp? http://www.elastic.co/guide/en/elasticsearch/reference/master/mapping-timestamp-field.html#_store_index_2 |
@@ -5,15 +5,6 @@ The routing field allows to control the `_routing` aspect when indexing | |||
data and explicit routing control is required. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a note saying that _routing
is stored but not indexed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually looks like it is stored AND indexed
@clintongormley I pushed a new commit addressing your comments. For |
Meta fields were locked down to not allow exotic options to the underlying field types in elastic#8143. This change fixes the docs to no longer refer to the old settings. closes elastic#10879
Meta fields were locked down to not allow exotic options to the
underlying field types in #8143. This change fixes the docs
to no longer refer to the old settings.
closes #10879